Information processing system, information processing method, medium, and management device

ABSTRACT

The present invention is to realize a simple communication connection. A shooting system S includes: a display device 2 configured to change identifiers periodically so as to present an identifier; a management server 1 configured to share the identifier with the display device 2; and a user terminal 4 configured to acquire the identifier presented on the display device 2 when an identifier acquisition operation by a user is detected, and to transmit, to the management server 1, the acquired identifier and an operation instruction to operate a camera 3 identified by the acquired identifier. The management server 1 includes an information control block 114 which performs control to associate image data acquired with the camera 3 based on the operation instruction transmitted by the user terminal 4 with the identifier presented on the display device 2 when the identifier acquisition operation by the user is detected.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based upon and claims the benefit of priority under35 USC 119 of Japanese Patent Application No. 2019-157044, filed on Aug.29, 2019, and Japanese Patent Application No. 2020-021841, filed on Feb.12, 2020, the entire disclosure of which, including the description,claims, drawings, and abstract, is incorporated herein by reference inits entirety.

BACKGROUND 1. Field

The present invention relates to an information processing system, aninformation processing method, a medium, and a management device.

2. Related Art

Recently, identifiers such as two-dimensional barcodes displayed onscreens have been widely used. As an example, there is a technique forreading a two-dimensional barcode to identify a communicationdestination. For example, Japanese Patent Application Laid-Open No.2019-110602 discloses that two-dimensional barcodes respectivelydisplayed on a first device and a second device are read by a thirddevice to identify a communication destination between devices. Thisenables a communication connection between devices to be establishedwithout requiring each user to enter a communication destinationmanually. Further, for example, since the communication connection isthus established between devices, any one of devices can be used tocontrol the other devices remotely.

SUMMARY

According to the first aspect of the present invention, there isprovided an information processing system including: a presentationdevice configured to change identifiers periodically so as to present anidentifier; a management device configured to share the identifier withthe presentation device; and a communication device configured toacquire the identifier presented on the presentation device when anidentifier acquisition operation by a user is detected, and to transmit,to the management device, (i) related information of the acquiredidentifier and (ii) an operation instruction to operate an informationacquisition device identified by the acquired identifier, wherein themanagement device has a processor configured to identify the informationacquisition device based on the related information of the identifierreceived from the communication device, and operate the identifiedinformation acquisition device based on the operation instructionreceived from the communication device.

According to the second aspect of the present invention, there isprovided an information processing method performed by a systemincluding a presentation device, a management device, and acommunication device, including: causing the presentation device tochange identifiers periodically so as to present an identifier; causingthe presentation device and the management device to share theidentifier presented on the presentation device with each other; causingthe communication device to acquire the identifier presented on thepresentation device when an identifier acquisition operation by a useris detected, and transmitting, to the management device, (i) relatedinformation of the acquired identifier and (ii) an operation instructionto operate an information acquisition device identified by the acquiredidentifier; and causing the management device to identify theinformation acquisition device based on the related information of theidentifier received from the communication device, and to operate theidentified information acquisition device based on the operationinstruction received from the communication device.

According to the third aspect of the present invention, there isprovided a non-transitory computer-readable recording medium with aprogram stored therein, the program causing a computer of a managementdevice connected to a presentation device and a communication device toexecute: sharing an identifier periodically changed by and presented onthe presentation device; receiving, from the communication device, (i)related information of the acquired identifier and (ii) an operationinstruction to operate an information acquisition device identified bythe acquired identifier; identifying the information acquisition devicebased on the relate information of the identifier of received from thecommunication device; and operating the identified informationacquisition device based on the operation instruction received from thecommunication device.

According to the fourth aspect of the present invention, there isprovided a management device connected to a presentation device and acommunication device, and including a processor, the processor of themanagement device executing: sharing an identifier periodically changedby and presented on the presentation device; receiving, from thecommunication device that acquires the identifier presented on thepresentation device, (i) related information of the acquired identifierand (ii) an operation instruction to operate an information acquisitiondevice identified by the acquired identifier; identifying the based onthe related information of the identifier received from thecommunication device; and operating the identified informationacquisition device based on the operation instruction received from thecommunication device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system configuration diagram illustrating the configurationof a shooting system S according to one embodiment of the presentinvention.

FIG. 2 is a sequence diagram illustrating an outline of the operation ofthe shooting system S according to one embodiment of the presentinvention.

FIG. 3 is a block diagram illustrating the hardware configuration of amanagement server 1 included in the shooting system S according to oneembodiment of the present invention.

FIG. 4 is a block diagram illustrating the hardware configuration of adisplay device 2 included in the shooting system S according to oneembodiment of the present invention.

FIG. 5 is a block diagram illustrating the hardware configuration of acamera 3 included in the shooting system S according to one embodimentof the present invention.

FIG. 6 is a block diagram illustrating the hardware configuration of auser terminal 4 included in the shooting system S according to oneembodiment of the present invention.

FIG. 7 is a functional block diagram illustrating a functionalconfiguration for executing shooting management processing in thefunctional configuration of the management server 1.

FIG. 8 is a table illustrating an example of a table 1821 as a datastructure stored in a management information storage block 182 of themanagement server 1.

FIG. 9 is a functional block diagram illustrating a functionalconfiguration for executing the shooting management processing in thefunctional configuration of the display device 2.

FIG. 10 is a functional block diagram illustrating a functionalconfiguration for executing the shooting management processing in thefunctional configuration of the camera 3.

FIG. 11 is a functional block diagram illustrating a functionalconfiguration for executing the shooting management processing in thefunctional configuration of the user terminal 4.

FIG. 12 is a part of a flowchart for describing a flow of the shootingmanagement processing in the management server 1.

FIG. 13 is another part of the flowchart for describing the flow of theshooting management processing in the management server 1.

FIG. 14 is the remaining part of the flowchart for describing the flowof the shooting management processing in the management server 1.

FIG. 15 is a flowchart for describing a flow of the shooting managementprocessing in the display device 2.

FIG. 16 is a flowchart for describing a flow of the shooting managementprocessing in the camera 3.

FIG. 17 is a part of a flowchart for describing a flow of the shootingmanagement processing in the user terminal 4.

FIG. 18 is the remaining part of the flowchart for describing the flowof the shooting management processing in the user terminal 4.

FIG. 19 is a part of a flowchart for describing a flow of live-viewdisplay processing in the management server 1.

FIG. 20 is a schematic diagram illustrating a display example of a pagedisplayed on the user terminal 4.

FIG. 21 is a part of a flowchart for describing a flow of processing formanaging the number of waiting people in the management server 1.

FIG. 22 is a schematic diagram illustrating an example of a status listand a waiting state list in the management server 1.

FIG. 23 is a part of a flowchart for describing a flow of identifierdisplay stop processing and camera adjustment processing of the displaydevice 2 performed by the management server 1.

FIG. 24 is a part of a flowchart for describing a flow of identifierdisplay resume processing of the display device 2 performed by themanagement server 1.

FIG. 25 is a schematic diagram illustrating an example of a pagedisplayed on the user terminal 4.

FIG. 26 is a schematic diagram illustrating a display example providedon the user terminal 4.

FIG. 27 is a schematic diagram illustrating an example of a shootingcompletion image displayed on the user terminal 4.

FIG. 28 is a schematic diagram illustrating an example of a list imageof captured photos displayed on the user terminal 4.

DETAILED DESCRIPTION OF THE INVENTION

An embodiment of the present invention will be described below withreference to the accompanying drawings.

[Overall System Configuration]

FIG. 1 is a system configuration diagram illustrating the configurationof a shooting system S according to one embodiment of the presentinvention.

As illustrated in FIG. 1, the shooting system S is configured to includea management server 1, a display device 2, a camera 3, a user terminal4, and an external device 5. The management server (management device)1, the display device 2 (presentation device), the camera 3 (informationacquisition device), and the user terminal 4 (communication device) arecommunicable with one another. This communication may be communicationcompliant with any standard. For example, this communication is realizedby any one of the Internet, a LAN (Local Area Network), and a mobilephone network, or a network obtained by combining these networks.

The management server 1 is a device having an arithmetic processingfunction and a communication function. For example, the managementserver 1 is realized by an electronic device such as a server or apersonal computer. Then, for example, the management server 1 operatesas a “management device” of the present invention.

The display device 2 is a device having an image display function and acommunication function. For example, the display device 2 is realized bya tablet type terminal, a digital signage, or an E-Ink display capableof electrically rewriting the display content. Then, for example, thedisplay device 2 operates as a “presentation device” of the presentinvention. Further, the display device 2 displays an identifier such asa two-dimensional barcode. For example, an identifier such as a QR code(registered trademark) is displayed as indicated by a two-dimensionalbarcode C in FIG. 1.

The camera 3 is a photographing device having a photographing functionand a communication function. For example, the camera 3 is realized byan electronic device such as a digital camera. Then, for example, thecamera 3 operates as an “information acquisition device” of the presentinvention. Here, the display device 2 and the camera 3 are installed inassociation with a location suitable for commemorative photos such as ashooting spot at which user U1 and user U2 can take and record photoswith a composition against a landscape L including buildings and a tree.

The user terminal 4 is a device having an arithmetic processingfunction, a communication function, and an identifier reading function.For example, the user terminal 4 is realized by a smartphone capable ofbeing carried by a user, a wearable device such as a smart watch, or adigital camera. Then, for example, the user terminal 4 operates as a“communication device” of the present invention. As an example, FIG. 1illustrates a state where user U1 of user U1 and user U2 is carrying andusing the user terminal 4.

An external device 5 is a device having an arithmetic processingfunction, a communication function, and an identifier reading function.For example, the external device 5 is realized by a tablet, a desktopcomputer, or the like. For example, the external device 5 operates as an“external device” of the present invention. As an example, a tablet typeexternal device 5 located in a remote place from the shooting system Sis illustrated in FIG. 1. The configuration of the external device 5 inthe embodiment is the same as that of the user terminal 4.

Although one pair of the display device 2 and the camera 3, and one userterminal 4 are illustrated in FIG. 1, it is assumed that multipledevices and terminals actually exist, respectively.

The shooting system S having this configuration performs “shootingmanagement processing.” Here, the shooting management processing is aseries of processing performed by a user to manage shooting andrecording using the camera 3.

An outline of this shooting management processing and informationtransmitted and received in the shooting management processing will bedescribed with reference to FIG. 2. FIG. 2 is a sequence diagramillustrating the outline of the shooting management processing.

First, the management server 1 and the display device 2 communicate witheach other to share an identifier (step A11 a, step A11 b). Further, thedisplay device 2 displays the shared identifier, for example, like thetwo-dimensional barcode C illustrated in FIG. 1 (step A12). Theidentifier displayed on this display device 2 is the identifierpresented to the user, which functions, for example, as a “presentedidentifier.” Here, identifiers are changed periodically to share anddisplay each identifier in the shooting management processing. Note thatsuch periodic identifier changes are omitted in FIG. 2 in order tobriefly describe the outline of the overall shooting managementprocessing. Note that the periodic identifier changes are not limited tomeaning that the same identifier is periodically presented. The periodicchange here indicates that an identifier is changed to anotheridentifier over time. In other words, it is indicated that an identifierpresented at first time and an identifier presented at second time laterthan the first time are different from each other.

In each of identifiers changed periodically, unique connectioninformation generated for each identifier is included. As an example, itis assumed in the following that this connection information is a uniqueURL (Uniform Resource Locator) generated for each identifier. Added tothis URL is information for identifying the installation location of thedisplay device 2 with the identifier displayed thereon (and the locationof the camera 3 paired with this display device 2).

The user terminal 4 reads the identifier displayed on the display device2 to acquire the information included in the identifier (step A13). Theidentifier read by this user terminal 4 is the identifier acquired bythe user terminal 4, which functions, for example, as an “acquiredidentifier.”

Based on the URL included in the read identifier, the user terminal 4establishes a communication connection to a site provided on themanagement server 1, and transmits recording instruction data (stepA14).

As described above, the information for identifying the installationlocation of the display device 2 (and the location of the camera 3paired with this display device 2) is added to this URL. Then, based onthe information added to the URL used by the user terminal 4, themanagement server 1 can identify a corresponding camera 3 as a target ofthis recording instruction.

Along with this communication connection, for example, the managementserver 1 also creates a user ID for identifying the name of a user (theuser name of user U1 in FIG. 1) of the user terminal 4 to which thecommunication connection is established by using this URL and causes theuser terminal 4 to store the user ID. For example, the management server1 stores the user ID in a connection management area of browser softwareof the user terminal 4 in the form of a cookie. After that, themanagement server 1 can identify the user terminal 4 by transmitting andreceiving this cookie to and from the user terminal 4.

The management server 1 transmits the received recording instructiondata to the identified camera 3 (step A15).

Based on the received recording instruction data, the camera 3 executesrecording of a shot image (step A16).

The camera 3 transmits, to the management server 1, recorded image dataobtained based on the received recording instruction data (step A17).Then, the management server 1 stores and manages the recorded image datareceived from the camera 3 in association with the user ID of the userterminal 4 from which the recording instruction data was transmitted.

Hereinafter, the management server 1 manages the recorded image dataassociated with the user ID in a state of being browseable on the userterminal 4 owned by the user corresponding to this user ID. Thisbrowseable state includes, for example, a state where a recorded imagebased on the recorded image data is displayed on the user terminal 4through a browser, and a state where the recorded image data isdownloaded to the user terminal 4 and a recorded image based on thisrecorded image data is displayed. Note that the user terminal 4 in thiscase is not limited to the user terminal from which the recordinginstruction data was transmitted, and the user terminal 4 may bedifferent from the user terminal which transmitted the recordinginstruction data as long as the user terminal is identified by the userID.

The management server 1 transmits recorded image data to the userterminal 4 to display, on the user terminal 4, a recorded image based onthe recorded image data (step A18).

The user terminal 4 displays the recorded image based on the recordedimage data received from the management server 1 (step A19). Asdescribed above, the transmission and display of this recorded image maybe realized either by displaying the recorded image through the browseror by downloading the recorded image data to the user terminal 4 todisplay the recorded image.

As described above, according to the shooting management processing, theuser ID used as a cookie upon communication connection through theidentifier can be used as information for identifying both the camera 3and the user terminal 4.

Therefore, the user can remotely control the camera 3 corresponding tothe identifier by reading this identifier once into the user terminal 4to establish the communication connection to the management server 1.

[Hardware Configuration]

Next, the hardware configuration of each device included in the shootingsystem S will be described with reference to FIG. 3, FIG. 4, FIG. 5, andFIG. 6, respectively.

FIG. 3 is a block diagram illustrating the hardware configuration of themanagement server 1 according to one embodiment of the shooting systemof the present invention.

As illustrated in FIG. 3, the management server 1 includes a CPU(Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (RandomAccess Memory) 13, a bus 14, an input/output interface 15, an input unit16, an output unit 17, a storage unit 18, a communication unit 19, and adrive 20.

The CPU 11 is a processor which executes various processing according toprograms recorded in the ROM 12 or programs loaded from the storage unit18 into the RAM 13. These programs are programs such as an operatingsystem and firmware which operate each unit of the management server 1,or application software which implements functional blocks to bedescribed later.

In the RAM 13, data necessary for the CPU 11 to execute variousprocessing and the like are also stored as appropriate.

The CPU 11, the ROM 12, and the RAM 13 are connected to one anotherthrough the bus 14. The input/output interface 15 is also connected tothis bus 14. The input unit 16, the output unit 17, the storage unit 18,the communication unit 19, and the drive 20 are connected to theinput/output interface 15.

The input unit 16 is composed of various buttons and the like to acceptuser's instruction operations and input various pieces of informationaccording to the accepted instruction operations.

The output unit 17 is composed of a display, a speaker, and the like tooutput images and sound. Note that the input unit 16 and the output unit17 may be integrated together, for example, by a touch panel.

The storage unit 18 is configured by a hard disk, a DRAM (Dynamic RandomAccess Memory), or the like to store various image data.

The communication unit 19 controls communication performed with anyother device. For example, as described above with reference to FIG. 1,the communication unit 19 controls communication performed betweenrespective devices included in the shooting system S.

A removable medium 101 such as a magnetic disk, an optical disk, or amagneto-optical disk, or a semiconductor memory is mounted onto thedrive 20 as appropriate. A program read by the drive 20 from theremovable medium 101 is installed in the storage unit 18 as necessary.Further, the removable medium 101 can also store various data such asimage data stored in the storage unit 18 in the same manner as thestorage unit 18.

FIG. 4 is a block diagram illustrating the hardware configuration of thedisplay device 2 according to one embodiment of the shooting system ofthe present invention.

As illustrated in FIG. 4, the display device 2 includes a CPU 21, a ROM22, a RAM 23, a bus 24, an input/output interface 25, an input unit 26,an output unit 27, a storage unit 28, and a communication unit 29. Here,the hardware function of each unit having the same name but differentonly in the reference numeral is equivalent to the hardware function ofeach unit included in the above-described management server 1.Therefore, redundant description will be omitted below.

FIG. 5 is a block diagram illustrating the hardware configuration of thecamera 3 according to one embodiment of the shooting system of thepresent invention.

As illustrated in FIG. 5, the camera 3 includes a CPU 31, a ROM 32, aRAM 33, a bus 34, an input/output interface 35, a storage unit 36, acommunication unit 37, and an imaging unit 38.

Though not illustrated, the imaging unit 38 includes an optical lensunit and an image sensor. The optical lens unit is composed of lensesthat collect light such as a focus lens and a zoom lens to shoot asubject.

The focus lens is a lens to form a subject image on a light-receivingsurface of the image sensor. The zoom lens is a lens to change the focallength freely within a certain range.

A peripheral circuit for adjusting setting parameters such as focalpoint, exposure, and white balance as necessary is also provided in theoptical lens unit. The image sensor is composed of a photoelectricconversion element, an AFE (Analog Front End), and the like.

The photoelectric conversion element is, for example, a CMOS(Complementary Metal Oxide Semiconductor) type photoelectric conversionelement or the like. The subject image is incident on the photoelectricconversion element from the optical lens unit. Then, the photoelectricconversion element photoelectrically converts (shoots) the subjectimage, accumulates an image signal for a certain time, and supplies, asan analog signal, the accumulated image signal sequentially to the AFE.

The AFE executes various signal processing such as A/D (Analog/Digital)conversion processing on this analog image signal. A digital signal isgenerated by the various signal processing, and output as an outputsignal of the imaging unit 38.

The hardware function of each of units other than the imaging unit 38,which has the same name but is different only in the reference numeral,is equivalent to the hardware function of each unit included in theabove-described management server 1 or the display device 2. Therefore,redundant description will be omitted below.

FIG. 6 is a block diagram illustrating the hardware configuration of theuser terminal 4 according to one embodiment of the shooting system ofthe present invention.

As illustrated in FIG. 6, the user terminal 4 includes a CPU 41, a ROM42, a RAM 43, a bus 44, an input/output interface 45, an input unit 46,an output unit 47, a storage unit 48, a communication unit 49, animaging unit 50, and a drive 51.

Here, the hardware functions of each unit and a removable medium 102having the same name but different only in reference numeral areequivalent to the hardware functions of each unit and the removablemedium included in the management server 1, the display device 2, andthe camera 3 described above. Therefore, redundant description will beomitted below.

[Functional Blocks]

Next, functional blocks of each device included in the shooting system Swill be described with reference to FIG. 7, FIG. 8, FIG. 9, FIG. 10, andFIG. 11.

FIG. 7 is a functional block diagram illustrating a functionalconfiguration for executing shooting management processing in thefunctional configuration of the management server 1 in FIG. 3.

Here, the shooting management processing is a series of processingperformed to manage shooting by a user using the camera 3 as describedabove.

As illustrated in FIG. 7, an identifier sharing block 111 and amanagement block 112 in the CPU 11 function to execute the shootingmanagement processing.

Further, when the shooting management processing is executed, anidentifier storage block 181 and a management information storage block182 are set in one area of the storage unit 18.

Though it may not be specifically mentioned below, data necessary torealize the shooting management processing is transmitted and receivedbetween these functional blocks appropriately in a timely manner.

In the identifier storage block 181, an identifier (for example, atwo-dimensional barcode) shared with the display device 2 is stored. Asdescribed above, the identifier is changed periodically. Further, asalso described above, the identifier includes a URL, and information ofthe installation location corresponding to the display device 2 with theidentifier displayed thereon (and the installation locationcorresponding to the camera 3 paired with this display device 2) isadded to the identifier.

A code ID as a unique ID is also added to the identifier. The code ID isused by the management block 112 to be described later to identify theorder of displaying the identifier. As the code ID, for example, anumber monotonically increasing each time the identifier is changed, orinformation capable of identifying the display order such as a timestampis used. In addition, for example, a random number such as a UUID(Universally Unique Identifier) may be used as the code ID in such amanner that the management block 112 stores this random number and theorder of displaying the identifier to identify the display order.

The identifier stored in the identifier storage block 181 is updatedappropriately by the identifier sharing block 111.

In the management information storage block 182, “managementinformation” as information used by the management block 112 to performmanagement in the shooting management processing is stored. A specificcontent of the management information will be described later in thedescription of the management block 112.

The identifier stored in the management information storage block 182 isupdated appropriately by the management block 112.

The identifier sharing block 111 shares the identifier changedperiodically with the display device 2 by the communication through thecommunication unit 19. The information such as the URL included in theidentifier periodically changed is newly generated by the managementblock 112 for each period. The identifier sharing block 111 converts, toan identifier, the information such as the new URL generated by themanagement block 112. Then, the identifier sharing block 111 transmitsthis identifier to the display device 2 so that the display device 2 canshare the identifier. Note that the length of each changing period canbe arbitrarily set. For example, the length of each period can be set intens of seconds (for example, every 30 seconds). The identifier sharingblock 111 also update the identifier stored in the identifier storageblock 181 each time the identifier is updated.

The management block 112 updates the management information stored inthe management information storage block 182, and performs management inthe shooting management processing based on this management information.In the following, description will be made by dividing the managementblock 112 into plural functional blocks. The management block 112 of theembodiment includes an identification block 113, an information controlblock 114, a management control block 115, an acceptance control block116, and a presentation control block 117.

The identification block 113 identifies the camera 3 based on theidentifier. For example, as described above, since the display device 2and the camera 3 are associated with each other as a pair, theidentification block 113 acquires the identifier to identify the displaydevice 2 sharing the identifier. Then, the identification block 113identifies the camera 3 associated with the identified display device 2as a target of the recording instruction.

The information control block 114 controls the installation location ofthe camera 3, the code ID included in the identifier, the user ID of theuser terminal 4 which establishes the communication connection to themanagement server 1 to transmit the recording instruction data, andrecorded image data acquired with the camera 3 in association with oneanother. For example, the management block 112 stores theabove-described pieces of information in a table 1821 of the managementinformation storage block 182 in association with one another.

Further, the information control block 114 generates an URL included ineach identifier and information to be added to the URL. Based on the URLgenerated by the information control block 114, the identification block113 performs processing for identifying the user terminal 4 whichestablished the communication connection and processing for identifyingthe camera 3 to which recording instruction data is transmitted.

The management control block 115 performs processing for managingrecorded image data obtained by the recording instruction. For example,the management control block 115 performs processing for transmittingthe recorded image data shot with the camera 3 to the user terminal 4 orthe external device 5 in which the same user name as that of the userterminal 4 is set. In other words, the user can cause the externaldevice 5 sharing the user ID to download the recorded image data.Further, the external device 5 may be specified in advance as a downloaddestination of the recorded image data.

The acceptance control block 116 determines whether the recordinginstruction using the camera 3 is accepted or not based on apredetermined condition. For example, during accepting a recordinginstruction from the user to take a photo(s), the acceptance controlblock 116 performs control not to accept recording instructions fromother user terminals 4.

The presentation control block 117 performs processing on information tobe displayed on the display device 2. For example, the presentationcontrol block 117 performs processing for transmitting the identifier tobe displayed on the display device 2, processing for displayinginformation related to shooting, and the like.

Note that the processing performed by the identification block 113, theinformation control block 114, the management control block 115, theacceptance control block 116, and the presentation control block 117 maybe described below as the processing of the management block 112.

The details of the management information stored in the managementinformation storage block 182 will be described with reference to FIG.8. FIG. 8 is the table 1821 illustrating an example of the datastructure of the management information stored in the managementinformation storage block 182. As illustrated in FIG. 8, the table 1821includes, as the management information, “installation location,” “codeID,” “user ID,” and “recorded image data.”

The installation location and the code ID are stored in the table 1821as new records when the recording instruction from the user terminal 4is newly accepted. As for the user ID, when a cookie is transmitted andreceived through communication with the user terminal 4, a user IDcorresponding to this cookie is added to and stored in a correspondingrecord. Further, the recorded image data is added to and stored in acorresponding record when a shot is taken with the camera 3.

Note that the table 1821 may be updated (for example, the registrationof the installation location, and the like) based on operations by anoperator of the management server 1 accepted by the input unit 16.

The installation location is information indicative of the installationlocation of the display device 2 with the identifier displayed thereon(and the installation location of the camera 3 paired with this displaydevice 2). For example, as illustrated in FIG. 8, the name of a spot atwhich the display device 2 (and the camera 3) is installed can be usedas the installation location. In the embodiment, the display device 2(and the camera 3 paired with this display device 2) is identified basedon the information of this installation location, but the presentinvention is not limited thereto. For example, there is a case where twoor more cameras 3 (for example, two or more cameras 3 having differentshooting angles, respectively) exist at the same installation location.In this case, each camera 3 may be identified by further using angleinformation in addition to the information of this installationlocation.

Alternatively, instead of the information of this installation location,a unique ID assigned to each display device 2 or a unique ID assigned toeach camera 3 may be used. Then, the IDs respectively corresponding tothe display device 2 and the camera 3 may be linked to each installationlocation to identify the display device 2 (and the camera 3 paired withthis display device 2).

The code ID is a unique ID assigned to each identifier. The details ofthe code ID is as described above in the description of the identifiersharing block 111. For example, as illustrated in FIG. 8, a numbermonotonically increasing each time the identifier is changed can beused. As described above, the installation location and the code ID areinformation added to the URL.

The user ID is a unique ID for identifying each user terminal 4,respectively. For example, as illustrated in FIG. 8, a combination ofnumerals and alphabets or the like can be used. When the user terminal 4establishes communication connection based on a URL corresponding to theidentifier, a browser of the user terminal 4 stores the user ID as acookie. Then, once the user terminal 4 stores any user ID as a cookie,this user terminal 4 continues to use this user ID even whenestablishing a communication connection based on any other URL. In otherwords, the user ID once stored as a cookie is not rewritten. Therefore,the user ID functions as a unique ID for identifying each user terminal4, respectively.

The recorded image data is image data obtained as a result of shootingand recording with the camera 3. For example, as illustrated in FIG. 8,a file name of the recorded image data and image data itself as the filecan be used. The data format of the recorded image data is notparticularly limited, and any data format can be used according to theenvironment in which the shooting system S is implemented, and the like.

The management block 112 updates these pieces of management informationstored in the management information storage block 182, and performsmanagement in the shooting management processing based on thismanagement information. Specifically, the management block 112identifies the camera 3 as a target of the recording instruction(operation instruction) based on information added to the URL used bythe user terminal 4 for communication connection. Further, after thecommunication connection is established, the management block 112identifies the user terminal 4 which transmitted the recordinginstruction data (operation instruction data) based on the user IDtransmitted to and received from the user terminal 4 as the cookie.

Further, based on the code ID added to the URL used for thecommunication connection, the management block 112 determines whether toaccept the recording instruction data transmitted from the user terminal4 which established the connection using this URL or not.

When the camera 3 accepts recording instruction data from any one ofplural user terminals 4, the management block 112 does not acceptrecording instructions from the other user terminals 4 until processingbased on this recording instruction data is ended. Then, after recordedimage data is obtained, recording instruction data from any other userterminal 4 is accepted anew.

Note that recording instruction data from the user terminal 4 may beaccepted several times until the predetermined condition is met.Further, recording instruction data from any other user terminal 4 maybe accepted after the predetermined condition is met. For example, thispredetermined condition is that the recording instruction data isaccepted a predetermined number of times or that a preset time haspassed. This enables the user of the user terminal 4 to transmit therecording instruction data over and over again even after transmittingthe recording instruction data until the predetermined condition is met.

Further, when recording instruction data from any other user terminal 4is newly accepted, the management block 112 accepts the recordinginstruction data of the user terminal 4, which first read the identifierand established communication connection, with priority over that of anyother user terminal 4. Since code IDs can be used to identify thedisplay order of identifiers, the management block 112 refers to thecode IDs to figure out that identifiers have been cyclically displayedon the display device 2 in order of a first identifier, a secondidentifier, a third identifier, and so on.

The management block 112 accepts recording instruction data from a userterminal 4 that read the first identifier with priority. For example,when the recording instruction data from the user terminal 4 that readthe first identifier is not accepted, the management block 112 does notaccept recording instruction data from another user terminal 4 that readthe second identifier until the prior recording instruction data isaccepted within an effective period.

This enables the user terminal 4 that read the identifier earlier thanthe other user terminals 4 to transmit recording instruction data to thecamera 3 with priority.

The management block 112 transmits the accepted recording instructiondata to the camera 3 to cause the camera 3 to execute recording.Further, the management block 112 manages a recorded image based onrecorded image data obtained by the recording instruction data in such amanner that the recorded image can be browsed on the user terminal 4from which the recording instruction data was transmitted.

Here, an example of using a cookie to associate the user terminal 4 andthe camera 3 with each other in the management server 1 will bedescribed. The information control block 114 of the management server 1issues a URL and generates, as an identifier, a two-dimensional barcodecorresponding to the URL and information added to the URL. Thistwo-dimensional barcode is displayed on the display device 2. The CPU 41of the user terminal 4 uses the imaging unit 50 to shoot thistwo-dimensional barcode and convert the barcode part to the URL. Then,this converted URL is used to give the communication unit 49 aconnection request to the management server 1.

When the connection request from the user terminal 4 is detected, theidentification block 113 confirms a user ID transmitted from the userterminal 4 and determines whether it is an invalid access or not. Whenit is not the invalid access, the identification block 113 issues acookie. Further, the identification block 113 stores, in the managementinformation storage block 182, the user terminal 4, for which a user IDcorresponding to the cookie is set, and the installation location of acamera 3, to which recording instruction data is transmitted among theinstallation locations of plural cameras 3, in association with eachother. In this example of using the cookie, it is assumed that a“session ID” is embedded in the cookie and the management server 1 sideadopts a “session management” method in which various pieces ofinformation are stored in the management information storage block 182in association with the session ID.

FIG. 9 is a functional block diagram illustrating a functionalconfiguration for executing the shooting management processing in thefunctional configuration of the display device 2 of FIG. 4.

As illustrated in FIG. 9, an identifier sharing block 211 and a displaycontrol block 212 in the CPU 21 function to execute the shootingmanagement processing.

Further, when the shooting management processing is executed, anidentifier storage block 281 is set in one area of the storage unit 18.

Though it may not be specifically mentioned below, data necessary torealize the shooting management processing is transmitted and receivedbetween these functional blocks appropriately in a timely manner.

In the identifier storage block 281, an identifier shared with themanagement server 1 is stored. The identifier stored in the identifierstorage block 281 is updated appropriately by the identifier sharingblock 211.

The identifier sharing block 211 shares periodically changed identifierswith the management server 1 by the communication through thecommunication unit 29. Since the details of these identifiers andsharing of the identifiers are described above in the description of themanagement server 1, redundant description will be omitted here.

The display control block 212 performs control to cause the output unit27 to display the identifier stored in the identifier storage block 281.As described above, the identifier is updated, for example, in a cycleof tens of seconds. Therefore, the display control block 212 updates anddisplays the latest identifier shared with the management server 1 inthis cycle.

FIG. 10 is a functional block diagram illustrating a functionalconfiguration for executing the shooting management processing in thefunctional configuration of the camera 3 of FIG. 5.

As illustrated in FIG. 10, a recording instruction response block 311and a shooting control block 312 in the CPU 31 function to execute theshooting management processing. Further, when the shooting managementprocessing is executed, a recorded image storage block 361 is set in onearea of the storage unit 36.

Though it may not be specifically mentioned below, data necessary torealize the shooting management processing is transmitted and receivedbetween these functional blocks appropriately in a timely manner.

In the recorded image storage block 361, a recorded image as image dataobtained by the imaging unit 38 taking a photo under the control of theshooting control block 312 is stored.

The recording instruction response block 311 accepts recordinginstruction data from the management server 1. This recordinginstruction data corresponding to the identifier displayed on thedisplay device 2 paired with the camera 3 is transmitted from the userterminal 4. Upon accepting the recording instruction data, the recordinginstruction response block 311 instructs the shooting control block 312to perform shooting and recording. Further, the recording instructionresponse block 311 transmits, to the management server 1, recorded imagedata obtained by the shooting control block 312 executing shooting andrecording.

Based on the instruction from the recording instruction response block311, the shooting control block 312 performs control to drive theimaging unit 38 so as to execute shooting and recording. Thus, imagedata desired by the user of the user terminal 4 (for example, an imageincluding the user of the user terminal 4 as a subject image against adesired landmark) is obtained as recorded image data. The shootingcontrol block 312 outputs this recorded image data to the recordinginstruction response block 311 and stores the recorded image data in therecorded image storage block 361.

FIG. 11 is a functional block diagram illustrating a functionalconfiguration for executing the shooting management processing in thefunctional configuration of the user terminal 4 of FIG. 6.

As illustrated in FIG. 11, an identifier acquisition block 411, arecording instruction block 412, and an image generation block 413 inthe CPU 41 function to execute the shooting management processing.

Further, when the shooting management processing is executed, anidentifier storage block 481 and a recorded image storage block 482 areset in one area of the storage unit 48.

Though it may not be specifically mentioned below, data necessary torealize the shooting management processing is transmitted and receivedamong these functional blocks appropriately in a timely manner.

In the identifier storage block 481, information included in anidentifier read by the identifier acquisition block 411 is stored. Theinformation included in the identifier stored in the identifier storageblock 481 is updated appropriately by the identifier acquisition block411.

In the recorded image storage block 482, a recorded image shot with thecamera 3 based on recording instruction of the recording instructionblock 412 is stored.

The identifier acquisition block 411 reads an identifier such as atwo-dimensional barcode displayed on the display device 2 based on anoperation of the user of the user terminal 4 accepted by the input unit46. This reading is realized by decoding a two-dimensional barcode,included in the image shot by the imaging unit 50, using a knownalgorithm (for example, an algorithm complying with the two-dimensionalbarcode standard). The identifier acquisition block 411 stores, in theidentifier storage block 481, information included in thetwo-dimensional barcode.

The recording instruction block 412 transmits, to the management server1, recording instruction data for the camera 3 based on an operation ofthe user of the user terminal 4 accepted by the input unit 46.

The image generation block 413 receives, from the management server 1,recorded image data shot based on the recording instruction datatransmitted from the recording instruction block 412. Then, the imagegeneration block 413 generates a recorded image based on the receivedrecorded image data and displays the generated recorded image on theoutput unit 47.

The recording instruction block 412 and the image generation block 413use a URL included in the identifier read by the identifier acquisitionblock 411 to establish communication connection to the management server1 in order to transmit the recording instruction data and receive therecorded image data, respectively. Note that a browser may beautomatically launched by taking the opportunity that the identifieracquisition block 411 has read the URL from the identifier.

[Operation]

Although the user terminal 4 is described above, the external device 5has the same configuration. Next, the operation of each device includedin the shooting system S will be described with reference to FIG. 12 toFIG. 25.

FIG. 12, FIG. 13, and FIG. 14 are flowcharts for describing a flow ofthe shooting management processing executed by the management server 1having the functional configuration of FIG. 7 in the shooting system S.

First, the identifier sharing block 111 executes processing for puttingan identifier such as a two-dimensional barcode in a shared state withthe display device 2 (step S11). For example, the identifier is put inthe shared state with the display device 2 by transmitting, from themanagement server 1, the identifier to be shared with the display device2.

Next, the identifier sharing block 111 determines whether time is up ornot (step S12). Specifically, when a predetermined time (for example, 30seconds) has passed after the start of the shooting managementprocessing, the identifier sharing block 111 determines that time is up.“Time is up” means that the cycle to change the identifier has arrived.When the identifier sharing block 111 determines that the cycle tochange the identifier has arrived (step S12→Yes), the procedure proceedsto step S13. On the other hand, when the identifier sharing block 111determines that the cycle to change the identifier has not arrived yet(step S12→No), the procedure proceeds to step S17.

When the identifier sharing block 111 determines that the cycle tochange the identifier has arrived, a new identifier is generated (stepS13), and the generated identifier is written into the identifierstorage block 181 to update the content of the identifier storage block181 (step S14).

After that, the identifier sharing block 111 transmits the newlygenerated identifier to the display device 2 (step S15), and restart atimer (step S16). Then, the procedure returns to step S11 to share thenewly generated identifier with the display device 2.

On the other hand, when the identifier sharing block 111 determines thatthe cycle to change the identifier has not arrived yet, the informationcontrol block 114 of the management block 112 determines whether aconnection request using a URL corresponding to the identifier from theuser terminal 4 is detected or not (step S17). When the informationcontrol block 114 determines that the connection request is detected(step S17→Yes), the procedure proceeds to step S18. On the other hand,when the information control block 114 determines that the connectionrequest is not detected (step S17→No), the procedure returns to stepS11.

When the information control block 114 determines that the connectionrequest is detected, recording instruction data is transmitted to thecamera 3 through the management server 1, and a page on which arecording instruction icon linked to the function of causing the camera3 to record a shot image is laid out is transferred to the user terminal4 that made the connection request by taking the opportunity to receivethis recording instruction data (step S18). In the embodiment, the pagetransferred here includes text indicating that the number of times ofacceptable recording instruction data is twice (see FIG. 20).

The information control block 114 shares a user ID with the userterminal 4, and registers the user ID in the management informationstorage block 182 (step S19). The user ID is data in a cookie formatincluding the user name as the destination upon issuing/transmitting thepage on which the above-mentioned recording instruction icon is laidout. Then, the management block 112 starts a 60-second timer (step S20).

The information control block 114 determines whether time is up or not(step S21). In the embodiment, it is determined that time is up, forexample, when 60 seconds as the predetermined time has passed. When itis determined that time is up (step S21→Yes), the procedure proceeds tostep S36. On the other hand, when it is determined that time is not up(step S21→No), the procedure proceeds to step S22.

When determining that time is not up in step S21, the informationcontrol block 114 determines whether recording instruction data isreceived from the user terminal 4 by the user touching the recordinginstruction icon or not (step S22). When it is determined that recordinginstruction data is received (step S22→Yes), the procedure proceeds tostep S23. On the other hand, when it is determined that recordinginstruction data is not received (step S22→No), the procedure returns tostep S21.

When determining that recording instruction data is received, theinformation control block 114 executes processing for continuing thecountdown (step S23). Then, based on information added to the URL usedby the user terminal 4 to establish the communication connection, theidentification block 113 of the management block 112 identifies thecamera 3 as the target of the present recording instruction (step S24).At this time, the identification block 113 identifies the user terminal4 as the transmission source of the recording instruction data based onthe user ID transmitted and received as a cookie.

Based on a code ID added to the URL used by the user terminal 4 toestablish the communication connection, the acceptance control block 116of the management block 112 determines whether the camera 3 side canaccept recording instruction data received from the user terminal 4 ornot (step S25). When it is determined that the camera 3 side cannotaccept recording instruction data (step S25→No), the procedure proceedsto step S26.

When determining that the camera 3 side cannot accept recordinginstruction data, the acceptance control block 116 transfers, to theidentified user terminal 4, a page indicative of not being able to beaccepted (step S26), and the procedure returns to step S21. On the otherhand, when it is determined that the camera 3 side can accept recordinginstruction data, the procedure proceeds to step S27.

The information control block 114 transmits the accepted recordinginstruction data to the camera 3 as the target of the recordinginstruction (step S27). After that, the information control block 114receives recorded image data shot and recorded with the camera 3according to the recording instruction (step S28).

The information control block 114 registers, in the managementinformation storage block 182, the recorded image data and the number ofreceptions received in association with the identifier (step S29). Thisidentifier is acquired by the user terminal 4 to perform the recordinginstruction. When recorded image data is received for the first timeafter the processing in step S21, “1” is stored in the managementinformation storage block 182 as count information. Similarly, whenrecorded image data is received for the second time, “2” is stored inthe management information storage block 182 as count information.

The information control block 114 determines whether the number ofreceptions exceeds a preset number of times or not (step S30). When itis determined that the number of receptions does not exceed the presetnumber of times (step S30→No), information for displaying the pageincluding the recording instruction icon is transferred to the userterminal 4 (step S31). Here, the recording instruction icon is replacedwith text indicating that the number of times of acceptable recordinginstruction data is once on the transferred page.

When it is determined that the number of receptions exceeds the presetnumber of times (step S30→Yes), the management control block 115generates information for displaying a confirmation image page (stepS32). A confirmation image is generated from the recorded image databased on image data obtained by reducing image information such as thedisplay size, the resolution, and the like. Further, it is desired thatthe confirmation image page with the confirmation image displayedthereon should have a page structure not to be able to keep the recordinside the user terminal 4. The management control block 115 transfers aconfirmation image display page to the user terminal 4 that transmittedthe recording instruction data (step S33).

The management control block 115 determines whether a transmissionrequest for recorded image data is received from the user terminal 4 ornot (step S34). For example, the transmission request is a downloadrequest for a recorded image selected by the user. When the transmissionrequest is received (step S34→Yes), corresponding recorded image data istransferred to the user terminal 4 (step S35), and the procedure returnsto step S11. On the other hand, when the transmission request forrecorded image data is not received (step S34→No), the procedure returnsto step S11 without transferring recorded image data.

Next, a case where it is determined in step S21 that time is up will bedescribed. As illustrated in FIG. 13, when it is determined that time isup (step S21→Yes), the procedure shifts to step S36.

When it is determined that time is up, the management control block 115determines whether recorded image data is registered in the managementinformation storage block 182 or not (step S36). When it is determinedthat the recorded image data is registered in the management informationstorage block 182 (step S36→Yes), the procedure proceeds to step S32. Onthe other hand, when it is determined that recorded image data is notregistered in the management information storage block 182 (stepS36→No), the procedure proceeds to step S37.

When determining that recorded image data is not registered in themanagement information storage block 182, the management control block115 transfers, to the user terminal 4, a notification page to notify theuser terminal 4 that time is up (step S37), and erases information onthe user ID as the target of the present processing stored in themanagement information storage block 182 (step S38). After that, theprocedure returns to step S11.

One example of the shooting management processing executed by themanagement server 1 is described above. Referring next to FIG. 15,processing executed by the display device 2 will be described. FIG. 15is a flowchart for describing a flow of the shooting managementprocessing executed by the display device 2 having the functionalconfiguration of FIG. 9 in the shooting system S.

First, it is assumed that the identifier sharing block 211 is in a stateof sharing an identifier with the management server 1 (step S221).Specifically, the display device 2 operates with an identifiertransmitted as a shared target from the management server 1.

The display control block 212 executes processing for displaying, on theoutput unit 27, an identifier as a two-dimensional barcode shared withthe management server 1 (step S222). When an E-Ink display is adopted asthe output unit 27, the display of the identifier can be continuedsemipermanently without power supply after voltage is applied only onoutput.

The identifier sharing block 211 determines whether a new identifier isreceived from the management server 1 or not (step S223). When it isdetermined that a new identifier is received (step S223→Yes), theprocedure returns to step S221. When it is determined that any newidentifier is not received (step S223→No), the procedure returns to stepS222 to continue the display of the identifier.

Referring next to FIG. 16, processing executed by the camera 3 will bedescribed. FIG. 16 is a flowchart for describing a flow of the shootingmanagement processing executed by the camera 3 having the functionalconfiguration of FIG. 10 in the shooting system S.

The recording instruction response block 311 determines whetherrecording instruction data is received or not (step S331). When it isdetermined that recording instruction data is received (step S331→Yes),the procedure proceeds to step S332. On the other hand, when it isdetermined that recording instruction data is not received (stepS331→No), the procedure returns to a state of waiting for acceptance ofrecording instruction data.

The recording instruction response block 311 determines whetherrecording instruction data is acceptable or inacceptable (step S332).When it is determined to be acceptable (step S332→Yes), the procedureshifts to step S333. When it is determined to be inacceptable (stepS332→No), the procedure shifts to step S335.

When the recording instruction response block 311 determines thatrecording instruction data is acceptable, the shooting control block 312executes recording processing (step S333). In the embodiment, acountdown for a predetermined time is performed after recordinginstruction data is received from the management server 1, and shootingand recording are performed after the countdown.

As a response to the recording instruction data, the recordinginstruction response block 311 transmits, to the management server 1,recorded image data obtained as a result of shooting and recording (stepS334). After that, the procedure returns to step S331.

When determining that recording instruction data is inacceptable (stepS332→No), the recording instruction response block 311 transmits, to themanagement server 1, information indicative of being inacceptable (stepS335). After that, the procedure returns to step S331.

Referring next to FIG. 17 and FIG. 18, processing executed by the userterminal 4 will be described. FIG. 17 and FIG. 18 are flowcharts fordescribing a flow of the shooting management processing executed by theuser terminal 4 having the functional configuration of FIG. 11 in theshooting system S.

The identifier acquisition block 411 determines whether there is auser's operation to read an identifier or not (step S411). When it isdetermined that there is a user's operation to read an identifier (stepS411→Yes), the procedure proceeds to step S413. On the other hand, whenthere is no user's operation to read an identifier (step S411→No), theprocedure proceeds to step S412. When determining that there is nouser's operation to read an identifier, the identifier acquisition block411 determines whether an identifier has been already read in the pastprocessing or not (step S412). When it is determined that an identifierhas been already read (step S412→Yes), the procedure proceeds to stepS414. On the other hand, when it is determined that any identifier hasnot been read yet (step S412→No), the procedure returns to step S411.

When determining that there is a user's operation to read an identifier,the identifier acquisition block 411 reads the identifier displayed onthe display device 2 based on this reading operation (step S413).

The recording instruction block 412 determines whether a connectionrequest to the management server 1 from the user is made or not (stepS414). When it is determined that the connection request is made (stepS414→Yes), the procedure proceeds to step S415. On the other hand, whenit is determined that no connection request is made (step S414→No), theprocedure returns to step S411.

When determining that the connection request to the management server 1from the user is made, the recording instruction block 412 transmits theconnection request to the management server 1 (step S415), and inresponse, receives the page on which the recording instruction icontransferred from the management server 1 is laid out (step S416). Thisrecording instruction icon is linked to the function of transmittingrecording instruction data to the camera 3 through the management server1 by detecting a touch operation of the user on the icon and causing thecamera 3 to record a shot image by taking the opportunity to receivethis recording instruction data.

The recording instruction block 412 displays, on the output unit 47, thepage on which the recording instruction icon is laid out (step S417).The recording instruction block 412 shares a user ID with the managementserver 1, and registers the user ID in the identifier storage block 481(step S418).

The recording instruction block 412 determines whether a recordinginstruction from the user is given to the camera 3 or not (step S419).When it is determined that no recording instruction is given (stepS419→No), the procedure proceeds to step S420. On the other hand, whenit is determined that the recording instruction is given (stepS419→Yes), the procedure proceeds to step S421.

When determining that no recording instruction is given, the recordinginstruction block 412 determines whether time is up or not (step S420).For example, the recording instruction block 412 determines that time isup when receiving a notification page being out of time from themanagement server 1. When determining that time is up (step S420→Yes),the recording instruction block 412 performs control to display anout-of-time notification page (step S426). Further, the recordinginstruction block 412 determines whether shooting using the camera 3 wasperformed or not (step S427). When it is determined that shooting wasalready performed (step S427→Yes), the procedure proceeds to step S428.On the other hand, when it is determined that shooting was not performed(step S427→No), the shooting management processing on the user terminal4 is ended. When it is determined in step S420 that time is not up (stepS420→No), the procedure returns to step S419.

The recording instruction block 412 transmits, to the management server1, recording instruction data based on the user's operation (step S421).

The management server 1 receives recording instruction data, and therecording instruction block 412 determines whether a recordinginstruction based on this recording instruction data is accepted or not(step S422). When determining that the recording instruction isinacceptable (step S422→No), the recording instruction block 412displays, on the output unit 47, an inacceptable page to indicate thatthe recording instruction is inacceptable (step S423). Then, theshooting management processing on the user terminal 4 is ended.

When the recording instruction block 412 determines that the recordinginstruction is accepted by the management server 1 (step S422→Yes), theprocedure proceeds to step S424.

The recording instruction block 412 displays the confirmation image pagereceived from the management server 1 (step S424). On the confirmationimage page, the confirmation image of an image shot and recorded withthe camera 3 as a result of transmitting the recording instruction datafrom the user terminal 4 to the camera 3 through the management server 1is laid out.

The recording instruction block 412 determines whether the number ofshots of the camera 3 is equal to or more than a predetermined number oftimes or less than the predetermined number of times (step S425). Whenit is determined that the number of shots is less than the predeterminednumber of times (step S425→No), the procedure returns to step S419.

When it is determined that the number of shots is equal to or more thanthe predetermined number of times (step S425→Yes), the procedureproceeds to step S428.

The recording instruction block 412 determines whether an imageselection operation is performed by the user or not (step S428). When itis determined that an image selection is performed by the user (stepS428→Yes), the procedure proceeds to step S429. When it is determinedthat no image selection is performed by the user (step S428→No), theshooting management processing on the user terminal 4 is ended.

The image generation block 413 requests the management server 1 totransmit a recorded image (step S429). The image generation block 413receives, from the management server 1, the recorded image shot based onthe recording instruction (step S430).

The image generation block 413 displays the received recorded image onthe output unit 47 (step S431). Then, the shooting management processingon the user terminal 4 is ended.

As described above, according to the shooting management processing ofthe embodiment, the identifier used to identify both the camera 3 andthe user terminal 4 is periodically changed and displayed on the displaydevice 2 near the shooting spot in a format like a two-dimensionalbarcode. Thus, the user can perform communication control and remotecontrol of the camera 3 to execute shooting/recording merely by usingthe imaging unit provided in the user terminal 4 to read the displayedidentifier.

Further, according to the shooting management processing, an informationinput device such as the camera 3 in a shared state on the network canbe temporarily operated by using the identifier periodically changed. Inaddition, according to the shooting management processing, since thecamera 3 located in a place far away from the user is used to performshooting, the whole group including a friend(s) can be shot or shootingat an angle difficult for the user terminal to shoot can be performed.Although processing for displaying a recorded image on the user terminal4 is mainly described above, the same processing is performed when therecorded image is displayed on the external device 5.

[Configuration Examples]

The shooting system S configured above includes the display device 2,the management server 1, the user terminal 4 capable of being carried bythe user, and the camera 3.

The display device 2 is a presentation device which presents anidentifier while changing identifiers periodically.

The management server 1 is a management device which shares, with thedisplay device 2, the identifier periodically changed by and presentedon the display device 2.

The user terminal 4 is a communication device which acquires theidentifier presented on the display device 2 when an identifieracquisition operation by the user is detected, and transmits, to themanagement server 1, the acquired identifier and a recording instructionfor acquiring information.

The camera 3 is an information acquisition device operated based on therecording instruction received by the management server 1 to acquireimage data.

The management server 1 includes the information control block 114 whichperforms control to associate the image data acquired with the camera 3based on the recording instruction transmitted from the user terminal 4with the identifier presented on the display device 2 when theidentifier acquisition operation by the user is detected.

Thus, the identifier is periodically changed so that this identifier canbe used as information for identifying both the camera 3 and the userterminal 4. In other words, information on communicationprotocol-specific connection partners exchanged upon network connectionis linked to the control permissions of the network connection devices.

This enables the user to realize communication connection and remotecontrol of the camera 3 by reading the identifier once.

In a conventional general technique, the user needs to read pluraltwo-dimensional barcodes, respectively, to realize communicationconnection between plural devices, for example, for the purpose ofremote control or the like.

In other words, the user needs to do reading work many times, and it iscomplicated for the user. In contrast, according to the presentinvention, the user can realize remote control between plural devices byreading the identifier once.

The management server 1 further includes the management control block(first management control block) 115 which manages information acquiredby the camera 3 operated based on the recording instruction inassociation with the identified user terminal 4 or the external device 5corresponding to the identified user terminal 4.

This enables the user to refer to the information acquired by the camera3 on the device used by the user such as the user terminal 4.

The camera 3 includes an imaging unit which captures an image in alocation identified by the identifier as a shooting range. The camera 3acquires, as information, recorded image data including the usercarrying the user terminal 4 in the shooting range based on therecording instruction.

This enables the user to refer to a recorded image shot with the camera3 to include the user himself or herself.

The recording instruction in the shooting system S includes aninstruction to cause the camera 3 to capture images continuously. Themanagement server 1 includes the management control block (secondmanagement control block) 115 which manages plural recorded images,captured by the instruction to capture images continuously, inassociation with the identified user terminal 4 or the external device 5corresponding to the identified user terminal 4.

This enables the user to refer to recorded images such as continuousstill images or a video shot continuously with the camera 3.

The plural recorded images in the shooting system S are plural recordedimages recorded upon receipt of the recording instruction. The userterminal 4 or the external device 5 corresponding to the user terminal 4includes the input unit 46 (selection unit, instruction unit) whichselects a specific recorded image from among the captured pluralrecorded images and instructs the management server 1 to transmit theselected specific recorded image.

This enables the user to refer to the plural recorded images and acquirea desired recorded image through the user terminal 4 or the externaldevice 5. The shooting system S includes plural user terminals 4, andthe management server 1 further includes the acceptance control block(first acceptance control block) 116 which, when the camera 3 isidentified based on an identifier received from a user terminal 4,performs control not to accept the recording instruction from any userterminal 4 other than the user terminal 4 that transmitted the recordinginstruction to the identified camera 3. Thus, exclusive use of thecamera 3 by each user can be realized.

The shooting system S includes plural user terminals 4, and when thesame identifier is transmitted from two or more user terminals 4, theacceptance control block (second acceptance control block) 116 performscontrol to accept the recording instruction from one user terminal 4that first transmitted the identifier with priority over the other userterminals 4.

Thus, the order of use of the camera 3 can be determined fairlyaccording to the reading order.

The management server 1 identifies the user terminal 4 and the displaydevice 2 based on the content of an acquired identifier received fromthe user terminal 4 and the content of a presented identifier sharedwith the display device 2.

This enables the management server 1 to use the identifier received fromthe user terminal 4 and the identifier shared with the display device 2as information for identifying both the camera 3 and the user terminal4.

[Modifications]

Note that the present invention is not limited to the embodimentdescribed above, various modifications and improvements capable ofachieving the object of the present invention are included in thepresent invention. For example, the above-described embodiment can bemodified to contain modifications as illustrated below. Further,modifications illustrated below can also be combined.

<First Modification>

In the embodiment described above, it is assumed that a single stillimage is shot with the camera 3, but the present invention is notlimited thereto. For example, continuous shooting may be performed withthe camera 3 to obtain continuous still images or to obtain a videocomposed of these continuous still images as respective frames. Further,each user may make a selection of which is shot, the single still image,the continuous still images, or the video, based on the recordinginstruction from the user terminal 4.

This enables the user to shoot a still image or a video selectivelyaccording to his or her intention.

Further, continuous still images or a video obtained by shooting may bebrowseable on the user terminal 4. This enables the user to give therecording instruction at desired timing while using the video or thelike to be referred to on the user terminal 4 as a live-view image tocheck his or her facial expression or pose.

Specific processing of the first modification will be described. FIG. 19is a part of a flowchart for describing a flow of live-view displayprocessing by the management server 1. The flowchart illustrated in FIG.19 is a substitute for processing step S18 in the flowchart of FIG. 12.

In the first modification, after the connection request for the URLcorresponding to the identifier is detected in step S17, the procedureproceeds to step S101. The identification block 113 identifies thecamera 3 based on the identifier, and the management control block 115requests the identified camera 3 to transfer a live-view image (stepS101).

In response to the transfer request for a live-view image, themanagement control block 115 receives the live-view image sequentiallytransmitted from the camera 3, generates a page on which a live-viewdisplay area of displaying the live-view image and the recordinginstruction icon are laid out, and transmits the page to the userterminal 4 that made the connection request (step S102). FIG. 20 is aschematic diagram illustrating an example of a page transferred from themanagement server 1 and displayed on the output unit 47 of the userterminal 4 (or the display unit of the external device). A page asillustrated in FIG. 20 is displayed on the user terminal 4 or theexternal device 5. In the example illustrated in FIG. 20, a live-viewimage is displayed within the frame of a live-view image 471. Inaddition to the live-view image 471, a recording instruction icon 472,text indicative of the time available for shooting, and text indicativeof the remaining number of shots (twice) are displayed. After processingstep S102, the procedure proceeds to step S19. Hereinafter, the sameprocessing as that of the above-mentioned embodiment described withreference to FIG. 12 is executed.

As described above, in the first modification, the management server 1renders continuously acquired recorded images as a live-view image insuch a manner as to be referable on the identified user terminal 4 orthe external device 5 corresponding to the identified user terminal 4.Then, the user terminal 4 further includes the communication unit 49which receives images sequentially captured with the camera 3 and theoutput unit 47 which displays a live-view image based on the imagesreceived by a receiver.

This enables the user to give the recording instruction at desiredtiming while checking his or her facial expression or pose in thelive-view image.

<Second Modification>

In the embodiment described above, the example in which when a recordinginstruction is accepted, control is performed not to accept anotherrecording instruction of any other user terminal 4 even if a connectionrequest from the user terminal 4 is received is described, but thepresent invention is not limited thereto. For example, informationexcept for that indicative of being inacceptable may also be provided tothe user terminal 4 concerned.

Specific processing of a second modification will be described. FIG. 21is a part of a flowchart for describing a flow of processing by themanagement server 1 to manage the number of waiting people. Theflowchart illustrated in FIG. 21 is performed between step S17 and stepS18 in the flowchart of FIG. 12.

In the second modification, after the connection request for the URLcorresponding to the identifier is detected in step S17, theidentification block 113 determines whether the camera 3 at theinstallation location identified by the URL is timer counting to preparefor shooting at present or not (step S111). When it is determined thatthe identified camera 3 is timer counting (step S111→Yes), the procedureproceeds to step S112. On the other hand, when it is determined not tobe timer counting (step S113→No), the procedure proceeds to step S18.

When determining that the identified camera 3 is timer counting, theidentification block 113 refers to a status list 1822 and a waitingstate list 1823 of the camera 3 (step S112). The status list 1822 andthe waiting state list 1823 are managed in the management informationstorage block 182. FIG. 22 is a schematic diagram illustrating anexample of these lists managed by the management server 1. The statuslist 1822 of FIG. 22 indicates the status of use (whether to be timercounting or not) of each camera 3, and the waiting state list 1823indicates whether the camera 3 is available at present or not, orindicates a state of waiting for use (i.e., waiting state) when thecamera 3 is unavailable at present.

In FIG. 22, “Code ID” in the status list 1822 is information foridentifying the camera 3, and “Count Flag” indicates whether timercounting is being performed at present or not. The code ID correspondingto count flag “0” indicates that the camera 3 identified by this code IDis not timer counting, while the code ID corresponding to count flag “1”indicates that the camera 3 identified by this code ID is timercounting. “User ID” in the waiting state list 1823 identifies the userwho operates the user terminal 4. “Transmission Time of BeingReady-to-Wait” indicates the time of transmitting, to the managementserver 1, that the user terminal 4 is ready to wait. “Waiting Flag”indicates whether a user waiting for use of the camera 3 is present ornot, where flag “0” indicates that no user waiting for use is present,and flag “1” indicates a user waiting for use is present. In the exampleof FIG. 22, the camera 3 identified by code ID “00120” indicates thatshooting/recording processing by user ID “abc1” is already completed andanyone can use the camera 3 at present. On the other hand, the camera 3identified by code ID “00121” and the camera 3 identified by code ID“00122” both indicate that a user waiting for use is present,respectively. Note that two users with respective user IDs “efg1” and“abc1” are waiting for use of the camera 3 identified by code ID “00121”and have already booked use of the camera 3 next, and one user with userID “abc1” is waiting for use of the camera 3 identified by code ID“00122” and has already booked use of the camera 3 next.

The management control block 115 transfers, to the user terminal 4, apage on which text saying that another user is using the camera 3, thenumber of waiting people, a countdown value, and a ready-to-wait/notready-to-wait icon are laid out (step S113).

The management control block 115 determines whether informationindicative of being ready to wait is received from the user terminal 4or not (step S114). When it is determined that the ready-to-waitinformation is received from the user terminal 4 (step S114→Yes), theprocedure proceeds to step S115. When it is determined that theready-to-wait information is not received from the user terminal 4 (stepS114→No), the procedure returns to step S11.

The management control block 115 updates the waiting state list 1823 insuch a manner, for example, as to accept that of the latest transmissiontime of being ready to wait with priority over the others (step S115).As specifically indicated in FIG. 22, the camera 3 being in the waitingstate, the user ID of the user terminal 4 that transmitted theready-to-wait information, and the time at which the user transmittedthe ready-to-wait information are input, and the waiting flag of thecamera 3 concerned is changed from 0 to 1.

The management control block 115 transfers, to the user terminal 4 thattransmitted the ready-to-wait information, a page on which text sayingthat another user is using the camera 3, the number of waiting people,and a countdown value are laid out (step S116). The number of waitingpeople is calculated by counting the number of waiting flags for eachcode ID. After this transfer processing, the procedure returns to stepS11.

According to the second modification, the user can grasp the current usestatus of the camera 3.

<Third Modification>

In the embodiment described above, the identifier displayed by thedisplay device 2 is changed periodically, but the present invention isnot limited thereto. Control to stop the display of the identifierduring the operation of the camera 3 by the user may be added.

Specific processing of a third modification will be described. FIG. 23is a part of a flowchart for describing a flow of identifier displaystop processing and camera adjustment processing of the display device 2performed by the management server 1. The flowchart illustrated in FIG.23 is performed between step S20 and step S21 in the flowchart of FIG.13.

After the processing for starting the 60-second timer in step S20, thepresentation control block 117 transmits, to the display device 2corresponding to the code ID, an instruction to stop the identifierdisplay (step S121). It is assumed that the display device 2 at thistime is displaying the identifier acquired by the user terminal 4 afterbeing acquired.

The presentation control block 117 determines that the 60-second timeris up or not (step S122). When it is determined that the timer is up(step S122→Yes), the procedure proceeds to step S13 to generate a newidentifier. On the other hand, when it is determined that the timer isnot up (step S122→No), the procedure proceeds to step S123.

When determining that the timer is not up, the presentation controlblock 117 determines whether recording instruction data from the userterminal 4 is received or not (step S123). When it is determined that norecording instruction is received (step S123→No), the procedure proceedsto the processing for determining whether time is up or not in step S21of FIG. 13. On the other hand, when it is determined that recordinginstruction data is received (step S123→Yes), the procedure proceeds tostep S124.

The presentation control block 117 transmits, to the display device 2,an instruction to start a 5-second timer (step S124).

The information control block 114 transmits shooting conditionadjustment instructions to the camera 3 (step S125), and the procedureproceeds to step S23.

When receiving the adjustment instructions transmitted in step S124, theshooting control block 312 of the camera 3 uses a period in which thedisplay device 2 counts the time by the 5-second timer to execute theshooting condition adjustment processing of the camera 3 during thisperiod. The shooting conditions such as the ISO sensitivity, the shutterspeed, and the white balance are adjusted according to the externalenvironment.

The flow of processing for changing the display of the identifier on thedisplay device 2 to the display of the timer start is described above.Next, the timing of displaying another identifier in the thirdmodification will be described. FIG. 24 is a part of a flowchart fordescribing a flow of identifier display resume processing of the displaydevice 2 performed by the management server 1. The flowchart illustratedin FIG. 24 indicates processing in step 33 and later performed afterprocessing step S32 in the flowchart of FIG. 14, that is, processing onthe display device 2 performed after the processing for generating theconfirmation image page by the management server 1 and before theprocessing for transferring the confirmation image page to the userterminal 4.

The information control block 114 generates a new identifier (stepS131), and updates the content of the management information storageblock 182 (step S132). In other words, the newly generated identifier isregistered in the management information storage block 182.

The presentation control block 117 transmits the newly registeredidentifier to the display device 2 (step S133). The identifier sharingblock 211 of the display device 2 registers the received identifier inthe identifier storage block 281 to share the identifier between themanagement server 1 and the display device 2. The display control block212 of the display device 2 displays the newly shared identifier. Inother words, the new identifier is displayed on the display device 2 bytaking the opportunity for the user terminal 4 to transmit recordinginstruction data to the management server 1.

The identifier sharing block 111 starts the timer (step S134). Afterthat, the procedure proceeds to step S17 of FIG. 12 again. Thesubsequent processing is the same as that in FIG. 12.

As described above, the third modification is configured as follows:

The management server 1 further includes the presentation control block(presentation control block) 117 which controls the display device 2,paired with the camera 3 executing recording processing by recordinginstruction data, not to present the identifier when the recordinginstruction data is received.

Thus, the display device 2 paired with the camera 3 during execution ofthe recording processing no longer presents the identifier. This canprevent any user terminal 4 other than the user terminal 4 thattransmitted the recording instruction data from acquiring the sameidentifier and transmitting the same recording instruction data.

When the recording instruction is received a preset number of times fromthe user terminal 4 that transmitted the identifier, or when a presettime has passed after the recording instruction was received, thepresentation control block 117 controls the display device 2 to resumethe presentation of the identifier.

This enables each user to take plural photos during exclusive use of thecamera 3.

Further, when the recording instruction data is received, thepresentation control block 117 controls the display device 2 paired withthe camera 3 that executes recording processing to provide a countdowndisplay beginning at the start of the 5-second timer instead of theidentifier according to the received recording instruction data, and toadjust the shooting conditions of the camera 3 during this period.

This enables the user to grasp the time to acquire image data throughthe display device 2.

Further, the camera 3 can make proper adjustments according to theshooting environment. For example, the exposure at the time of shootingwith the camera 3 can be adjusted according to differences in brightness(daytime, evening, night) to acquire image data including the user underproper conditions.

<Fourth Modification>

In the embodiment described above, it is assumed that a recorded imageshot with the camera 3 is displayed alone. However, the presentinvention is not limited thereto, and the recorded image shot with thecamera 3 may also be displayed in various ways.

For example, based on the user ID saved as a cookie, a browser of theuser terminal 4 may display, in a thumbnail display format or the like,plural recorded images stored in management server 1 and correspondingto this user ID.

Next, specific processing of a fourth modification will be describedwith reference to FIG. 25 to FIG. 28.

Note that a flow of processing in the fourth modification to bedescribed below is the same as processing step S416 and later in FIG. 17to describe the processing of the user terminal 4.

When the page on which the recording instruction icon 472 is laid out isreceived from the management server 1, the recording instruction block412 displays, on the output unit 47, an image as illustrated in FIG. 25.FIG. 25 illustrates an example of an operation page image displayed instep S417 of FIG. 17. In this example, a touch is so detected that therecording instruction icon 472 used to transmit recording instructiondata and text indicative of the number of shots are displayed.

When the user touching the recording instruction icon 472 is detected,the recording instruction block 412 displays, on the output unit 47, animage to let the user know about shooting and recording. For example, animage illustrated in FIG. 26 is displayed. FIG. 26 is a schematicdiagram illustrating an example of a timer display image displayed onthe user terminal 4. In FIG. 26, the direction of the camera in adisplay 473 saying “Please look in the direction of the camera” meansthe direction of the shooting optical axis. A display 474 saying “Fiveseconds to shoot” means a count (the number of seconds) until shootingwith the camera 3 is performed. A recorded image acquired by the camera3 performing shooting and recording is transmitted to the managementserver 1.

When the confirmation image display page is received from the managementserver 1, the recording instruction block 412 displays, on the outputunit 47, an image as illustrated in FIG. 27. FIG. 27 is a schematicdiagram illustrating an example of a shooting completion image displayedon the user terminal 4. A thumbnail image 475 generated based on arecorded image is illustrated in FIG. 27. In addition to the thumbnailimage 475, icons 476 and 477 are also displayed to perform the nextoperation. In this example, the icon 476 used to give an instruction forone more shot, and the icon 477 used to give an instruction forproviding a list display of recorded images are displayed.

When the user's touch on the icon 476 to give the instruction for onemore shot is detected, the recording instruction block 412 displays theimage illustrated in FIG. 25 again. Further, when the user's touch onthe icon 477 to give the instruction for checking the list of recordedimages is detected, the recording instruction block 412 requests themanagement server 1 to transmit a page illustrating the list. Whenreceiving the page illustrating the list, the recording instructionblock 412 displays, on the output unit 47, images as illustrated in FIG.28. FIG. 28 is a schematic diagram illustrating an example of a listimage of captured photos displayed on the output unit 47 of the userterminal 4.

According to FIG. 28, it is found that two or more thumbnail images 475,478 acquired with the camera 3 appear on the same page. Further, an icon479 to proceed to the next step is displayed. When the recordinginstruction block 412 detects that the user selects an image, the imagegeneration block 413 executes processing for storing the image in therecorded image storage block 482. For example, the image generationblock 413 makes a request to the management server 1 for an uncompressedimage corresponding to the image selected by the user. The imagegeneration block 413 stores, in the recorded image storage block 482,the image received from the management server 1. This enables the userto check images shot by himself or herself at once. When the userselects the icon 479, the page moves to another page on whichquestionnaire results are input or the like, and then the shootingmanagement processing is ended.

<Fifth Modification>

In the embodiment described above, it is assumed that only a recordedimage shot with the camera 3 is displayed. However, the presentinvention is not limited thereto, and any other information may also bedisplayed.

For example, when there are many shooting spots such as in an amusementpark or a sightseeing spot, cameras 3 are installed at respectiveshooting spots. Then, information on how many cameras 3 among theseplural cameras 3 are used to take photos and obtain recorded images (orhow many cameras 3 among these plural cameras 3 are used to take photosbut not to obtain recorded images) may be displayed.

This enables the user to more enjoy shooting with the cameras 3 in sucha manner as to aim to go around all the plural shooting spots in theamusement park or the like.

In addition, for example, the management server 1 may synthesize atleast parts of two or more recorded images corresponding to this user IDand display a synthesized recorded image. In other words, the recordedimage may be displayed as a collage image. Further, in this case, apreviously crated image material (for example, a character image or thelike related to a shooting spot, or the like) may further besynthesized. This enables the user to enjoy images shot by himself orherself as one image. Particularly, when there are many shooting spotsand cameras 3 are installed at respective spots, the user can obtainsuch an image as to express that the user visited various spots.

In addition, for example, when any person other than the user of theuser terminal 4 appears in a recorded image, the management server 1 maydefocus an image area corresponding to this person or apply a mosaic tothe image area. For example, when a live-view display is provided likein the third modification described above, it is assumed that personspresent in a focused area based on the recording instruction from theuser terminal 4 by the user are the user and his or her friend(s).Alternatively, it is assumed that persons present in a preset area suchas a central area of the angle of view of the camera 3 are the user andhis or her friend(s).

Then, an image area corresponding to any other person present in anyother area may be defocused or applied with a mosaic.

This fifth modification is configured as follows:

The shooting system S includes plural cameras 3, and the managementserver 1 includes the management control block (third management controlblock) 115 which manages at least either the number of cameras 3 thataccepts a recording instruction or the number of cameras 3 that does notaccept the recording instruction in association with the user terminal 4or the external device 5 corresponding to the user terminal 4.

This enable the user to more enjoy shooting with the cameras 3 in such amanner as to aim to go around plural shooting spots in the amusementpark or the like.

Further, the management server 1 further includes the management controlblock (fourth management control block) 115 which synthesizes parts ofpieces of information acquired respectively by the plural cameras 3based on the recording instructions to manage synthesized information ina manner to be able to be referred to on the identified user terminal 4or the external device 5 corresponding to the identified user terminal4.

This enables the user to more enjoy images shot by himself or herself asone image.

<Sixth Modification>

In the embodiment described above, after recording instruction is givenfrom the user on the user terminal 4, the management server 1 determineswhether this recording instruction is accepted or not. However, thepresent invention is not limited thereto, and this determination may bemade by any other method.

For example, the user terminal 4 and the management server 1 communicatewith each other periodically regardless of the presence or absence of arecording instruction from the user to confirm whether it is in a stateof being able to accept the recording instruction or not. Then, after itis confirmed that the recording instruction is acceptable, a screen usedto accept the recording instruction may be displayed on the userterminal 4 for the first time.

This can prevent from giving a recording instruction meaninglesslyregardless of the fact that any recording instruction from the user isnot acceptable.

Further, in the state where any recording instruction is inacceptable,information on how many user terminals 4 capable of being identifiedbased on the number of identifiers previously displayed (that is, thenumber of user terminals 4 waiting for giving their recordinginstructions) may be displayed. This enables the user to grasp how longto wait for shooting with the camera 3.

In other words, this modification can improve user friendliness.

<Seventh Modification>

In the embodiment described above, it is assumed that the target towhich a recording instruction is given is the camera 3, and a recordedimage is obtained by the camera 3. However, the present invention is notlimited thereto, and any information acquisition device other than thecamera 3 may be targeted for a recording instruction to obtaininformation.

For example, an information acquisition device such as a recordingdevice for acquiring sound or a sensor for detecting temperature or thelike may be targeted for a recording instruction. This enables the userto obtain information such as sound or temperature based on therecording instruction in a manner to be able to be referred to on theuser terminal 4.

[Other Modifications]

The series of processing described above can be executed in hardware orsoftware.

In other words, the functional configurations of FIG. 7, FIG. 9, FIG.10, and FIG. 11 are just illustrative examples, and the presentinvention is not particularly limited thereto. The functionalconfiguration may be enough as long as the shooting system S includesfunctions capable of executing the above-described series of processingas a whole, and which functional block is used to realize each of thefunctions is not particularly limited to each of the examples of FIG. 7,FIG. 9, FIG. 10, and FIG. 11.

Further, one functional block may be configured as a single hardwarecomponent, a single software component, or a combination thereof.

The functional configuration in the embodiment is implemented by aprocessor which executes arithmetic processing, and processors capableof being used in the embodiment includes a processor configured by eachof various single processing units such as a single processor, amultiprocessor, or a multi-core processor, and a combination ofrespective of these various processing units with a processing circuitsuch as ASIC (Application Specific Integrated Circuit) or FPGA(Field-Programmable Gate Array).

When the series of processing is executed by software, a program toimplement the software is installed on a computer or the like from anetwork or a recording medium.

The computer may be a computer incorporated in dedicated hardware.Further, the computer may be, for example, a computer on which variousprograms are installed to execute various functions such as ageneral-purpose personal computer.

In addition to the removable medium 101 in FIG. 2 distributed separatelyfrom the device body to provide the program to the user, the recordingmedium including such a program may be a recording medium provided tothe user in a state where the recording medium is incorporated in thedevice body in advance. The removable medium 101 is, for example, amagnetic disk (including a floppy disk), an optical disk, amagneto-optical disk, or the like. The optical disk is, for example, aCD-ROM (Compact Disk-Read Only Memory), a DVD (Digital Versatile Disk),a Blu-ray (registered trademark) a Disc (Blu-ray disk), or the like. Themagneto-optical disk is an MD (Mini-Disk) or the like. Further, therecording medium provided to the user in a state of being incorporatedin the device body is, for example, each of the ROM 12, the ROM 22, theROM 32, and the ROM 42 in which the program is recorded in FIG. 3, FIG.4, FIG. 5, and FIG. 6, or a hard disk or the like included in each ofthe storage unit 18, the storage unit 28, the storage unit 36, and thestorage unit 48.

In this specification, a step of writing a program recorded on therecording medium may include processing executed in parallel orindividually without being necessarily performed in chronological orderas well as processing performed chronologically in this order.

While the embodiment and some modifications of the present inventionhave been described, these embodiment and modifications are not to limitthe technical scope of the present invention. The present invention cancarry out any other embodiment and modifications and can combine theaforementioned embodiment with each of the modifications. Further,various omissions and replacements can be made without departing fromthe scope of the present invention. These embodiments and modificationsare included in the scope of the invention described in thisspecification and in the scope equivalent to that of the inventiondescribed in the scope of claims.

What is claimed is:
 1. An information processing system comprising: apresentation device configured to change identifiers periodically so asto present an identifier; a management device configured to share theidentifier with the presentation device; and a communication deviceconfigured to acquire the identifier presented on the presentationdevice when an identifier acquisition operation by a user is detected,and to transmit (i) related information of the acquired identifier and(ii) an operation instruction to operate an information acquisitiondevice identified by the acquired identifier, to the management device,wherein the management device has a processor configured to identify theinformation acquisition device based on the related information of theidentifier received from the communication device, and operate theidentified information acquisition device based on the operationinstruction information received from the communication device.
 2. Theinformation processing system according to claim 1, wherein theprocessor of the management device further manages information acquiredby the information acquisition device based on the operation instructioninformation in association with the communication device or an externaldevice corresponding to the communication device.
 3. The informationprocessing system according to claim 1, wherein the informationacquisition device includes an imaging unit configured to capture animage in a location identified by the identifier as a shooting range,the information acquisition device has a processor configured to controlthe imaging unit so as to capture an image with a user included in theshooting range based on the operation instruction information and tocause the information acquisition device to acquire the captured image.4. The information processing system according to claim 3, wherein theoperation instruction information includes an instruction to cause theimaging unit to capture images continuously, and the processor of themanagement device manages a plurality of images, captured by theinstruction to capture images continuously, in association with thecommunication device or an external device corresponding to thecommunication device.
 5. The information processing system according toclaim 4, wherein the communication device and the external devicecorresponding to the communication device have respective processors,and the processor of the communication device or the processor of theexternal device corresponding to the communication device selects aspecific image from the plurality of captured images, and instructs themanagement device to transmit the selected specific image.
 6. Theinformation processing system according to claim 3, wherein thecommunication device further includes: a receiver configured to receiveimages sequentially captured by the imaging unit; and a displayconfigured to display a live-view image based on the images received bythe receiver.
 7. The information processing system according to claim 1,further comprising a plurality of communication devices, eachcommunication device corresponding to the communication device, whereinwhen the information acquisition device is identified based on therelated information of the identifier received from a firstcommunication device, the processor of the management device performscontrol not to accept operation instruction information from anycommunication device other than the first communication device.
 8. Theinformation processing system according to claim 1, wherein when themanagement device receives the related information of the identifier andthe operation instruction information, the processor of the managementdevice controls the presentation device sharing the received relatedinformation of the identifier not to present the identifier.
 9. Theinformation processing system according to claim 8, wherein when theoperation instruction information is received a preset number of timesfrom the communication device that transmitted the related informationof the identifier, or when a preset time has passed after the operationinstruction information was received, the processor of the managementdevice controls the presentation device to resume the presentation ofthe identifier.
 10. The information processing system according to claim8, wherein when the related information of the identifier and theoperation instruction information are received, the processor of themanagement device controls the presentation device sharing theidentifier corresponding to the received related information of theidentifier to present a time to execute information acquisitionprocessing by the information acquisition device, instead of theidentifier.
 11. The information processing system according to claim 10,wherein when the information acquisition device receives the operationinstruction information through the management device, the processor ofthe management device controls the information acquisition device tomake an adjustment related to information acquisition processing beforethe information acquisition device executes the information acquisitionprocessing.
 12. The information processing system according to claim 1,further comprising a plurality of communication devices, eachcommunication device corresponding to the communication device, whereinwhen related information of the same identifier is transmitted from theplurality of communication devices, the processor of the managementdevice performs control to accept the operation instruction informationfrom a communication device that first transmitted the relatedinformation of the identifier with priority over the other communicationdevices.
 13. The information processing system according to claim 1,further comprising a plurality of information acquisition devices, eachinformation acquisition device corresponding to the informationacquisition device, wherein the processor of the management devicemanages one of the number of information acquisition devices that acceptthe operation instruction information and the number of informationacquisition devices that do not accept the operation instructioninformation in association with the communication device or an externaldevice corresponding to the communication device.
 14. An informationprocessing method performed by a system including a presentation device,a management device, and a communication device, comprising: causing thepresentation device to change identifiers periodically so as to presentan identifier; causing the presentation device and the management deviceto share the identifier presented on the presentation device with eachother; causing the communication device to acquire the identifierpresented on the presentation device when an identifier acquisitionoperation by a user is detected, and to transmit, to the managementdevice, (i) related information of the acquired identifier and (ii) anoperation instruction to operate an information acquisition deviceidentified by the acquired identifier; and causing the management deviceto identify the information acquisition device based on the relatedinformation of the identifier received from the communication device,and to operate the identified information acquisition device based onthe operation instruction received from the communication device.
 15. Anon-transitory computer-readable recording medium with a program storedtherein, the program causing a computer of a management device connectedto a presentation device and a communication device to execute: sharingan identifier periodically changed by and presented on the presentationdevice; receiving, from the communication device that acquires theidentifier presented on the presentation device, (i) related informationof the acquired identifier and (ii) an operation instruction to operatean information acquisition device identified by the acquired identifier;identifying the information acquisition device based on the relatedinformation of the identifier received from the communication device;and operating the identified information acquisition device based on theoperation instruction received from the communication device.
 16. Amanagement device connected to a presentation device and a communicationdevice, and comprising a processor, the processor of the managementdevice executing: sharing an identifier periodically changed by andpresented on the presentation device; receiving, from the communicationdevice that acquires the identifier presented on the presentationdevice, (i) related information of the acquired identifier and (ii) anoperation instruction to operate an information acquisition deviceidentified by the acquired identifier; identifying the informationacquisition device based on the related information of the identifierreceived from the communication device; and operating the identifiedinformation acquisition device based on the operation instructionreceived from the communication device.